* Pin @types/react to current minor on stable branches in dependabot

Dependabot's lockfile-only strategy respects the existing semver range in
package.json. Because @types/react is declared as a caret range (e.g.
"^18.2.6", "^19.1.4"), dependabot proposes minor-version bumps to the type
definitions even though the paired `react` runtime stays on its current
minor. On 0.74-stable this broke TS compilation — bumping @types/react from
18.2.67 to 18.3.28 failed with a forwardRef inference error in
KeyboardExt.tsx (see PR #15911).

Add an ignore rule to each stable-branch entry so minor and major updates
of @types/react and @types/react-dom are filtered out of the grouped PR.
Only patch updates flow through, keeping the type definitions aligned with
the frozen React minor on each branch:

  0.74-stable: @types/react locked to 18.2.x
  0.81-stable: @types/react locked to 19.1.x
  0.82-stable: @types/react locked to 19.1.x
  0.83-stable: @types/react locked to 19.2.x
  0.84-stable: @types/react locked to 19.2.x

The main-branch entry is unchanged — it should continue to track upstream
React type releases.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* Extend dependabot ignore to react + react-native + react-test-renderer

The react runtime, its type defs, and the matching test renderer are
version-locked together on each stable branch. Bumping any one of them to
a different minor can break TS compilation or runtime compatibility, so
lock the full set on every stable-branch dependabot entry.

Also include react-dom / @types/react-dom defensively — they aren't
currently in any stable-branch package.json but will be pinned if added
later.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>